Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Upgrade min Bazel required and upgrade CI to use 2.1 #3239

Merged
merged 2 commits into from
Apr 21, 2020

Conversation

stephanwlee
Copy link
Contributor

@stephanwlee stephanwlee commented Feb 12, 2020

Bazel is now out of the beta mode (version 0.x). We want to depend on
1+ for better long term support in the future.

@stephanwlee stephanwlee force-pushed the bazel_up branch 2 times, most recently from d198845 to cac4926 Compare February 27, 2020 00:33
@stephanwlee stephanwlee marked this pull request as ready for review February 27, 2020 16:18
@bileschi bileschi requested a review from nfelt March 18, 2020 20:18
Copy link
Contributor

@nfelt nfelt left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I feel like there was some reason we'd been unsure if we wanted to do this, but I can't remember and maybe it was just my oversight - at any rate, LGTM.

@stephanwlee
Copy link
Contributor Author

This is the reason:
image

49m is too tight for our comfort and I wasn't sure if we should pursue this route. It just has to miraculously pass only once for cache to prolong our life with Travis but that's... not cool.

@nfelt
Copy link
Contributor

nfelt commented Apr 21, 2020

💥 💥 💥

caisq pushed a commit to caisq/tensorboard that referenced this pull request May 19, 2020
Bazel is now out of the beta mode (version 0.x). We want to depend on
1+ for better long term support in the future.
caisq pushed a commit that referenced this pull request May 27, 2020
Bazel is now out of the beta mode (version 0.x). We want to depend on
1+ for better long term support in the future.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants